Skip to content

fix(v9/nuxt): Do not drop parametrized routes (#17357) #17359

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 8, 2025

Conversation

s1gr1d
Copy link
Member

@s1gr1d s1gr1d commented Aug 8, 2025

I just found out Nuxt is dropping spans for catch-all routes.

related to #16843 (as we have parametrized routes since then)

backport of #17357

I just found out Nuxt is dropping spans for catch-all routes.

related to #16843 (as
we have parametrized routes since then)
@s1gr1d s1gr1d requested review from Lms24 and mydea August 8, 2025 11:09
Copy link
Member

@Lms24 Lms24 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I see, this is because .*)* in routes would test positive for path.extname? I wonder if we can make the file name check more robust instead. Not sure if the regex works well enough. Like for example check that it only contains alphanumeric values? Not sure if this is any better though, so happy to go with this as well for now.

@s1gr1d
Copy link
Member Author

s1gr1d commented Aug 8, 2025

this is because .*)* in routes would test positive for path.extname?

Yes exactly! theoretically, it would be also possible to put the regex just on the extname but I am not sure if this actually makes it more robust 🤔 There is only a limited set of how a parametrized route in Nuxt can look like.

@s1gr1d s1gr1d merged commit b3acba0 into v9 Aug 8, 2025
38 checks passed
@s1gr1d s1gr1d deleted the sig/v9-nuxt-filter-params branch August 8, 2025 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants